Skip to main content

Clips, Tracks & Collections

Track​

A Track is a full-length audio file - the complete recording of a song. Tracks are used as the source material for custom clipping, where a user selects a specific segment of a song to use (up to 60s). You can fetch a track using its trackId. Users are not permitted to listen to more than 60s of a song at a time via the Clips API.

Clip​

A Clip is a short selection of a Track (up to 60s in length). These are the fundamental unit of music that users add to their content. Every clip has a clipId that you use to request as a signed URL.

There are two kinds of clips: curated (designed by Feed's curation team) and custom (created by a user from a full track). See Curated vs. Custom Clips for details.

Collection​

A Collection is a curated grouping of clips, selected and maintained by Feed's curation team. Collections are the primary discovery path for music in Clips. You can request entire Collections from the API and let users browse them to find songs they want to use.

You can dive into all available Collections in Clips Studio and choose which ones to expose in your app, or copy IDs for specific songs that you want to offer.

How Collections Fit Into the Flow​

Collections do not return audio directly. When you fetch a Collection, the API returns a list of clipId and trackId values for the clips in that Collection. You then use those IDs in separate requests to fetch the actual audio URLs.

  • To fetch all Collections or a subset by ID, use the Fetch Collections endpoint.
  • To fetch the signed URL and metadata for a clip, use the Fetch Clips endpoint.

For a walkthrough of the full browse-and-fetch flow, see the how-to guide Browse Collections & Fetch a Clip.